HCL Lotus Expeditor wiki: Best Practices: Toolbars, global menus, view menus and popup menus

Toolbars, global menus, view menus and popup menus

Added by ~Frank Cishipipulettu on September 24, 2010 | Version 1

Actions ▼

There are multiple ways to create toolbars, menus, and popups. This article provides the recommended approach from the Expeditor user Interface team

Tags: ui, ux, user interface, best practices

ShowTable of Contents

HideTable of Contents

1 Global toolbars
2 View toolbars
3 Global menus, view menus, and popup menus

The number of options available when contributing toolbars and menus can be confusing when working in the Expeditor based products. To simplify the process of contributing these items, the Expeditor UI team recommends the following as best practices.

Global toolbars

Use org.eclipse.ui.actionSets, if the developer wants to add regular/standard type of toolbar button such as push, radio, toggle, pulldown buttons
Use com.ibm.rcp.ui.controlSets, if the developer wants to add arbitrary SWT control to toolbar, such as Text, Combo, StyledText, Browser controls
The use of org.eclipse.ui.menus is not supported for global toolbar in Expeditor for now

View toolbars

Use org.eclipse.ui.viewActions, if the developer wants to add regular/standard type of toolbar button such as push, radio, toggle, pulldown buttons.
Call IViewSite.getActionBars().getToolbarManager() and add a contribution to the toolbar manager , if the developer wants to add arbitrary SWT control to toolbar, such as Text, Combo, StyledText, Browser controls.
org.eclipse.ui.menus is not supported for view toolbar on Expeditor for now.

Global menus, view menus, and popup menus

Use org.eclipse.ui.actionSets, viewActions, popupMenus by default.
Use org.eclipse.ui.menus, only if you have a strong reason to use it. An example would be if the developer wants to display the menu even when the all the tabs(pages/perspectives) are closed.